I didn't run the project but I think the explanations are correct.

If I remember correctly how --runFast works, the first time that the user will run npm run watch on a clean project he will have to wait for the initial compilation even if webpack is started because not compiled files will exist yet. I think webpack will report an error message (in red).

So I don't know if you prefer to use --run so start webpack only when the first compilation of Fable is done.

I am mentioning that only in case you want to avoid a new user to have a red message printed on its first run.

I think I would probably add the content of package.json (just the interesting sections) in the documentation directly because, when reading the page I was looking at what npm run start does. Because, npm run start by itself can do anything.

+1